-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon Test: Only register testing module in Vite projects #29472
Addon Test: Only register testing module in Vite projects #29472
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile
message = 'Component tests failed'; | ||
} else if (crashed || (failed && errorMessage)) { | ||
message = ( | ||
if (globalThis.STORYBOOK_BUILDER?.includes('vite')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style: Consider using a more robust check like STORYBOOK_BUILDER === '@storybook/builder-vite'
instead of string includes
testResults: TestResult[]; | ||
error?: { message: string; name: string }; | ||
}>); | ||
} | ||
|
||
addons.add(PANEL_ID, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: Panel is still registered even when test provider is not available, which could lead to confusing empty UI state
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a47eaf8. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Closes #
What I did
The Testing module UI will now only be registered in Vite-based projects.
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>
Greptile Summary
This PR modifies the test addon to conditionally enable component testing functionality only for Vite-based Storybook projects, while maintaining the UI panel for all projects.
globalThis.STORYBOOK_BUILDER?.includes('vite')
incode/addons/test/src/manager.tsx
to gate test provider registrationTEST_PROVIDER_ID
now only occurs for Vite projectsPANEL_ID
remains available for all projects regardless of builder